This is a minor update which fixes a few bugs, all associated with the Window menu.
Times+ 1.1.1 fixes three minor bugs with the Window menu:
1) It no longer flickers when updated.
2) It properly re-positions a listed Window when that Window's name is updated.
3) It will properly modify a hyphen-first Window name such as "-MyWindow" so that adding it to the menu will not accidentally add a separator line. Size is still approx. 423K.
Times+ 1.1 Notes
Although not a major upgrade, Times+ 1.1 does include several enhancements.
• Window Menu •
Times+ now includes a Window menu. This menu has two commands previously found under Control. In addition, it lists all open MiniView windows, allowing you to easily select and bring any MiniView to front, even if it's hidden from view by another window.
• MiniView Enhancements •
MiniViews are now named after the Events they represent.
Also, MiniViews may now be "collapsed" to show only the window title bar and the Event Time. To collapse a MiniView, click in the zoom box. To expand it again, do the same.
• Changed Menu Names •
"Normal" to "FullView" (now command-F)
"Merge List With…" to "Merge Lists…"
"Export To…" to "Export Events…"
Size has increased by 13K from 1.0.1, to 423K. Unfortunately, the windows do not yet remember their positions. This will be included in the first major upgrade, when Times+ can open multiple files at once (among other significant changes).
Times+ 1.0.1 Notes
Times+ 1.0.1 is a minor update which fixes a potentially annoying quirk and reduces size by 30K.
I didn't include any form of window position code for Times+ 1.0. The windows were preset to their positions for 640x480 screens, but they neither remembered their new positions if a user moved them nor centered themselves on larger or smaller screens. A future version will include, among other things, windows which remember their positions. However, for now, I decided to add a method which centers all windows (except a couple dialogs) on screen according to the screen present when Times+ starts up. This isn't too big of a deal for users with 640x480 screens, but for users with classic Mac's this will be a lot better than the windows always opening off the monitor a bit. That's the annoying quirk.
Also, it was compiled with the latest version of Prograph Classic, 2.6. This, and cleaning up a bit after myself, saved about 30K. Times+ is now 410K. Still a bit big as far as apps go, but the good news is that there were no real bugs reported for the 1.0 release. That's the benefit of using Prograph and the Prograph System Classes.
Some users have reported needing more memory to run Times+ and/or big increases in speed and stability with more memory. On my machine it runs just fine with the 600K given, and even pretty good with only 500K, so my guess is that one or more extensions may be upsetting things, but I have not confirmed this yet. If you experience speed and stability problems with the normal RAM settings, increase the RAM given to Times+ and please report the problem to me.
Times+ 1.0 Notes
I thought that I better quickly explain something to Times+ users just in case this were to be a source of confusion.
Prograph (the development environment I used) automatically handles memory for the programmer for the most part, which is one of the great things about it.
However, this can result in a memory profile which looks dangerous to the end user. In other words, were you to look at the “About Macintosh” box from your Apple menu after Times+ had been running awhile, the Times+ memory partion may be full.
Don’t worry. This doesn’t mean that you need to increase the partion given to Times+. The Prograph memory manager does not clear blocks which are no longer used until it needs to. In other words, when you ask Times+ to do something (like save or open a new window) it will clear the unused memory blocks, and you will see plenty of free space AFTER performing the action.
The rule of thumb is that the partion should be large enough to hold Times+ (410K) plus the Event List you are opening, plus a bit of room to work in (say, 40K). If it’s at least that big, you should be completely fine.
